HTTP Trigger Node
The HTTP Trigger node acts as the execution entry point for HTTP-triggered workflows. It captures incoming HTTP request data and maps the request Body, QueryString, and Headers to workflow variables. Use this node when workflows need to be invoked via external HTTP calls rather than chatbot interactions.
How It Works
The HTTP Trigger node activates when an external system sends an HTTP request to the workflow endpoint. The node parses the incoming request and extracts three data components: the request body, query string parameters, and headers.
Each component is mapped to a separate workflow variable, making the data accessible to downstream nodes. This enables workflows to process data from external APIs, webhooks, or automated systems.
Unlike the User Prompt node which responds to chatbot messages, the HTTP Trigger node responds to programmatic HTTP requests. This makes it suitable for system-to-system integrations and automated workflow invocations.
Configuration
This node has no configuration parameters. It automatically extracts and maps HTTP request components to workflow variables.
Output
| Property | Description |
|---|---|
| Body | The HTTP request body content |
| QueryString | URL query parameters as key-value pairs |
| Headers | HTTP request headers as key-value pairs |
Each output is stored as a separate workflow variable accessible to downstream nodes.
Execution Lifecycle
| Phase | Behavior |
|---|---|
| Pre-execution | Awaits incoming HTTP request |
| Execution | Parses request, extracts Body, QueryString, and Headers |
| Post-execution | Maps extracted data to workflow variables, passes control downstream |
The node transitions from Not Run to Completed immediately upon receiving a valid HTTP request.
Usage Example
Webhook integration workflow:
HTTP Trigger → Data Transformation → Large Language Model → HTTP Response
External API processing workflow:
HTTP Trigger → Validation → Vector Search → Response Output
The request data flows from the trigger through processing stages, enabling automated document processing or API-driven AI responses.
Test HTTP Trigger Workflows
When testing a workflow that uses the HTTP Trigger node, the test panel displays input fields for HTTP request data. This simulates an external HTTP call to the workflow.
Test Input Fields
The test panel provides three sections for entering test data:
Query Parameters
Enter URL query parameters using the parameter input fields:
- Parameter Name: The query parameter key
- Parameter Value: The query parameter value
Multiple parameters can be added by clicking the add button.
Headers
Enter HTTP headers using the header input fields:
- Header Name: The HTTP header key
- Header Value: The HTTP header value
Multiple headers can be added by clicking the add button.
Request Body
Enter the JSON content for the HTTP request body in the body input field.
Run the Test
After entering the test data, click Run Test to execute the workflow. The HTTP Trigger node receives the provided parameters, headers, and body, then passes them to downstream nodes for processing.
Accessing Test Data in Nodes
Downstream nodes access the test data through system variables:
${state.data.system.body}Request body content${state.data.system.query_string}Query parameters as key-value pairs${state.data.system.headers}Request headers as key-value pairs
Limitations
- Single entry point: One HTTP Trigger node per workflow
- No authentication handling: Authentication must be managed at the API gateway level
- Synchronous execution: Request waits for workflow completion
- No configuration: Request parsing behavior cannot be customized
Best Practices
- Use HTTP Trigger for system-to-system integrations and webhook receivers
- Validate incoming request data in downstream nodes before processing
- Combine with HTTP Response nodes to return structured responses to callers
- Use User Prompt node instead for chatbot-driven workflows